FileMayor. by Chevza Pitch deck · v4.0.1 · 2026
Your AI can suggest.
Folders,
on command.
A command bar for your filesystem. Diagnose, plan, apply with rollback. Local-only. Mac, Windows, Linux.
live · v4.0.1 CLI · Desktop · PWA · MCP 25k+ npm installs
● scan → explain → cure → apply → undo filemayor.com
02 · The moment The gap between reasoning and acting
A new problem, every day
Your AI knows what to do
with your files.
It just can't do it.
today
"Here's a plan."
Model outputs a perfect-sounding list of moves. Stops at the filesystem boundary.
today
You, with a mouse.
Copy-paste the plan into Finder. Drag, rename, regret. No undo, no record.
today
Cloud "solutions."
Upload your home directory to a startup's S3 bucket. Pray it doesn't move the wrong thing.
The execution gap02 / 16
● 03 · The wedge One sentence
Your AI can suggest.
FileMayor can act —
with one undo to roll it back.
We are the execution layer for every AI assistant that already exists. Claude, ChatGPT, Cursor, Copilot — all write the plan. We are the safe way to run it.
filemayor v4.0.1 ▌
The wedge03 / 16
04 · The productFive verbs. Real output.
The entire surface area
Five verbs. In order.
Each verb is a deliberate gate. Reading, diagnosing, and planning never touch disk. Only apply writes, and it writes a journal. Undo reads that journal.
01
scan
filemayor scan
Read the directory. No moves, no cloud, no permission prompts beyond reading.
02
explain
filemayor explain
Health score 0–100 plus a plain-English issue list. Still no moves.
03
cure
filemayor cure --prompt
AI proposes specific moves with rationale. Plan, do not act.
04
apply
filemayor apply
Execute reversibly. Every move written to a session journal in your workspace.
05
undo
filemayor undo --all
Change your mind. One command reverses the whole session, journaled.
scan → explain → cure → apply → undo04 / 16
● 05 · The product, runningReal output. No screenshots.
Live
~/Downloads,
cured.
1,248 files, 4.2 GB.
Health: 22/100 → cured.
Wall clock: ~6 seconds.
· on a 2021 MacBook, offline.
offline journaled undo-any
$ filemayor explain ~/Downloads Scanned 1,248 files (4.2 GB) in 1.4s ──────────────────────────────────────────── Images 482 files · 1.2 GB Videos 12 files · 2.1 GB Documents 634 files · 0.8 GB ──────────────────────────────────────────── Diagnosis: 22/100 · 1,242 dupes · 3.8 GB recoverable → filemayor cure ~/Downloads --prompt "by type" $ filemayor cure ~/Downloads --prompt "by type" Gemini 2.0 Flash · 0.8s · metadata only → Move 63 screenshots → ~/Downloads/Screenshots → Consolidate installers → ~/Downloads/Software → Archive .zip > 12mo → ~/Archive/2024 → Trash 8 .crdownload artifacts Plan covers 112 files · ETA 3.1s · → apply $ filemayor apply [1/4] Screenshots 63 moved ✓ [2/4] Software 14 moved ✓ [3/4] Archive 27 moved ✓ [4/4] Trash 8 removed ✓ ──────────────────────────────────────────── Cure applied · 112 files · 3.1s journaled at .filemayor/journal/2026-04-26-1442.json ▌
same engine on CLI, Desktop, PWA05 / 16
06 · Why nowThree curves meeting
Why now
Three curves collided.
Curve 01 · Capability
Models that plan.
Tool-using LLMs are now reliable enough to propose specific filesystem operations — not hand-wavy advice.
Curve 02 · Protocol
MCP shipped.
A standard way for any assistant to call any local tool. Suddenly there's a socket, and we have the plug.
Curve 03 · Trust
Cloud fatigue.
Developers and IT both refuse to upload home directories. Local-first stopped being a niche — it's the requirement.
FileMayor sits exactly at the intersection. The engine has existed for two years; v4 is the version that opened the right doors at the right moment.
Why now06 / 16
● 07 · The moatLocal-first is structural, not a feature
The moat
Your files never leave
the machine.
·  Engine runs entirely on your machine.
·  AI sees metadata — names, sizes, paths. Never bytes.
·  Disable AI completely; the engine still works.
·  Three runtime dependencies. Zero runtime vulnerabilities.
·  Journal is local. Undo is local. License is local.
# competitors started cloud-first. # they cannot retrofit this posture. $ filemayor scan ~/Documents --offline ok airgap detected · proceeding ok ai disabled · heuristics only ok 1,082 files indexed · 0 bytes egress $ netstat -p filemayor (no connections) ▌
Local-first by construction07 / 16
● 08 · ArchitectureThe Chevza Doctrine
Architecture
Six layers between
any plan and your disk.
all green ● · 6 / 6
ok
LAYER 01
jailer
Path sandbox. Operations cannot escape the workspace root, even when the AI tries.
ok
LAYER 02
vault
Credentials, license, and any AI keys held in OS keychain. Never in plain files.
ok
LAYER 03
guardrail
Refuses destructive batches by policy. The AI can't propose what guardrail won't run.
ok
LAYER 04
halt
User-facing kill switch. One keystroke stops the in-flight session mid-apply.
ok
LAYER 05
architect
The constitution. The set of move-shapes the planner is allowed to suggest in the first place.
ok
LAYER 06
security
Audit log of every operation, every layer's verdict. Exportable for Team and Enterprise.
Answer to enterprise question #108 / 16
09 · DistributionOne engine, four surfaces
Distribution
One engine. Four surfaces.
We didn't bolt on AI. We exposed the engine the right way and let any client drive it.
surface 01
CLI
Canonical interface. Every command accepts --json; scriptable, CI-friendly.
$ npm install -g filemayor
surface 02
Desktop
Mac, Windows, Linux. Same engine, visual skin. Command bar at ⌘K.
filemayor.com/download
surface 03
PWA
Browser and mobile. Read-only triage on the go; full power when launched into desktop.
app.filemayor.com
surface 04 · new in v4
MCP
Claude Desktop and any MCP client. Diagnose, cure, apply, undo — as tools, locally.
@filemayor/mcp
Same five verbs. Same Doctrine. Same undo.09 / 16
10 · TractionOrganic. No paid acquisition.
Traction · pre-launch
Builders found us
first.
No paid ads. No launch post. The CLI is being installed organically — and the MCP angle is starting to compound.
25k+
npm installs · all-time
+700
installs · last 7 days
128
tests passing
0
runtime vulnerabilities
Three signals worth more than the absolute number: the MCP package is being installed by Claude Code users without us asking; retention on the CLI is measured in weeks-active, not first-install; and inbound from indie developers asking for Pro is real.
shape of curve > size of number10 / 16
11 · Business modelFree forever. Pro when ready.
Business model
Three tiers. One on-ramp.
Free is the wedge into the developer community. Pro is the wedge into individual power users. Team is the on-ramp to Enterprise.
tier 01
Free
$0 FOREVER
For individuals getting started.
  • Directory scan + analysis
  • Junk cleanup + undo last operation
  • Up to 50 files per operation
  • MCP server for personal use
tier 02 · most popular
Pro
$19 / MONTH
For power users who live in their filesystem.
  • Unlimited bulk operations
  • Watch mode — real-time automation
  • AI Curative Triad: explain → cure → apply
  • Full session journal + undo all
  • CSV / JSON export · priority support
tier 03
Team
$99 / MONTH
Up to 5 seats. The on-ramp to Enterprise.
  • Everything in Pro
  • Shared rule libraries
  • Audit-ready operation log
  • Priority support + SLA
  • SSO & fleet management on roadmap
14-day refund · USD, with local currency shown · annual plans on request $19 → $99 → Enterprise
Unit economics: positive on first Pro month, 8-month CAC payback model11 / 16
12 · MarketThree personas, all already in pain
Market
Who buys this. Today.
Persona 01 · Wedge
The developer.
"My ~/Downloads is a swamp and I already use Claude Code every day. Give me a verb."
Persona 02 · Expansion
The knowledge worker.
"I have 400 screenshots on my Desktop and one tax PDF I can't find. I don't want to learn anything."
Persona 03 · Enterprise on-ramp
The IT-adjacent team.
"One tool. Same behavior on the CLI, the desktop, and inside Claude. Audit log please."
TAM
27M devs
npm-using developers globally. Direct, addressable.
SAM
4M Claude users
AI-native users with native pain and native willingness to install local tools.
SOM · 36 mo
120k Pro
0.5% conversion of SAM. $27M ARR at current pricing.
Bottom-up: dev → power user → team → enterprise12 / 16
● 13 · FounderSolo, by design
Founder
One architect.
One codebase.
One decision-maker.
Lehlohonolo Goodwill Nchefu — Chevza. Built in South Africa, shipped to the world. Local-first means no servers to operate, which is why a single person can ship this and still answer the inbox. The engine is the product.
$ whoami Chevza (Lehlohonolo Goodwill Nchefu) Architect · Engineer · Support · Sales $ filemayor stats --since 2024 25,000+ installs · all-time 700+ installs · last 7 days 128 tests passing 0 runtime vulns 3 runtime deps $ filemayor where Built in South Africa. Privacy-first by default. ▌
solo founder 2 yrs on engine ZA · global
The reason a solo founder can ship this is the same reason it works.13 / 16
14 · RoadmapEach milestone is a pricing-tier unlock
Roadmap
The roadmap and the
revenue chart are the same chart.
Q3 · 2026 · NOW
Sharpen the edge.
  • Watch mode → GA
  • macOS notarization
  • Windows signing
  • Pro onboarding flow
Q4 · 2026
Open the team.
  • Team SSO (Google, Okta)
  • Shared rule libraries
  • Audit-log export
  • MCP catalog publish
Q1 · 2027
Earn the enterprise.
  • On-prem MCP server
  • Fleet management
  • SOC2 Type I
  • Enterprise pilot · 3 design partners
Q2+ · 2027
Scale the surface.
  • Mobile (iOS/Android wrappers)
  • Plugin SDK
  • SOC2 Type II
  • $1M ARR target
Tier unlock = revenue unlock14 / 16
15 · The askPre-seed · 18-month runway
Pre-seed
$1.2M.
18 months of runway. Three deliverables: one engineer, distribution, enterprise hardening.
hloninchefu@gmail.com · filemayor.com
Use of funds
  • 45%Engineer #2 · Desktop & Watch mode$540k
  • 25%Distribution · launch, content, dev-rel$300k
  • 15%Enterprise hardening · SSO, SOC2 prep$180k
  • 10%Founder salary · finally$120k
  • 5%Reserve · the unknown$60k
Milestone for next round: $50k MRR, three Team design partners, MCP catalog placement.
If you live in the filesystem — or fund people who do — let's talk.15 / 16
● FileMayor. by Chevza filemayor.com
Folders,
on command.
Try the product before you buy the company.
$ npm install -g filemayor ▌
Lehlohonolo Goodwill Nchefu · hloninchefu@gmail.com
v4.0.1 · 128 passing · 3 runtime deps · 0 runtime vulns